<html>
<head>
	<title> System Management & Security </title>
	<link rel="stylesheet" type="text/css" href="css/html.css">
	<link rel="stylesheet" type="text/css" href="css/docbook.css">
</head>


<body>
<h1> 1 FCAPS-ISO-Standard </h1>

<div class="TOC">
<dl>
	<dt><b>Table of Contents</b></dt>
	<dt>1.1 <a href="chapter1.html#FAULT">         Fault          </a></dt>
	<dt>1.2 <a href="chapter1.html#CONFIGURATION"> Configuration  </a></dt>
	<dt>1.3 <a href="chapter1.html#ACCOUNTING">    Accounting     </a></dt>
	<dt>1.4 <a href="chapter1.html#PERFORMANCE">   Performance    </a></dt>
	<dt>1.5 <a href="chapter1.html#SECURITY">      Security       </a></dt>
</dl>
</div>

<p>
	FCAPS is an acronym for Fault, Configuration, Accounting, Performance, Security which are the management categories 
	into which the ISO model defines network management tasks.
</p>


<!------------------ 1.1 Fault ---------------------------------------->
<div class="SECT1">
<h1 class="SECT1"><a id="FAULT" name="FAULT">1.1 Fault</a></h1>
<p>
A fault is an event which has a negative significance. The goal of fault management is to recognize, isolate, correct and log faults that occur in the network. Furthermore, it uses trend analysis to predict errors so that the network is always available. This can be established by monitoring different things for abnormal behavior.
</p>
<small>
Reference <a href="http://en.wikipedia.org/wiki/Fcaps"> http://en.wikipedia.org/wiki/Fcaps</a>
</small>
</div>


<!------------------ 1.2 Configuration ---------------------------------------->
<div class="SECT2">
<h1 class="SECT2"><a id="CONFIGURATION" name="CONFIGURATION">1.2 Configuration</a></h1>
<p>
Configuration management is a large function inside network management. It covers many areas. Configuration management is not just about a technology to collect device information but also about the processes needed for network support and operations.
Configuration management can be summarized as:
</p>

<ul>
	<li>
	<p>Device hardware and software inventory collection</p>
	</li>
	
	<li>
	<p>Device software management</p>
	</li>
	
	<li>
	<p>Device configuration collection, backup, viewing, archiving, comparison</p>
	</li>
	
	<li>
	<p>Detection of changes to configuration, hardware, or software</p>
	</li>
	
	<li>
	<p>Configuration change implementation to support change management</p>
	</li>
</ul>

<small>
Reference <a href="http://www.cisco.com/en/US/technologies/tk869/tk769/technologies_white_paper0900aecd806c0d88.html"> Cisco, Network Configuration Management</a>
</small>

</div>


<!------------------ 1.3 Accounting ---------------------------------------->
<div class="SECT3">
<h1 class="SECT3"><a id="ACCOUNTING" name="ACCOUNTING">1.3 Accounting</a></h1>
<p>
Accounting Management enables the measurement of the use of network services and the determination of costs to the service provider and charges to the customer for such use. It also supports the determination of prices for services.
Accounting Management includes the following function set groups:
</p>

<ul>
	<li>
	<p>Usage Measurement</p>
	</li>

	<li>
	<p>Tariffing/Pricing</p>
	</li>

	<li>
	<p>Collections and Finance</p>
	</li>

	<li>
	<p>Enterprise Control</p>
	</li>
</ul>

<small>
Reference <a href="http://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-M.3400-200002-I!!PDF-E&type=items">TU-T M.3400 (02/2000)</a>
</small>



</div>


<!------------------ 1.4 Performance ---------------------------------------->
<div class="SECT4">
<h1 class="SECT4"><a id="PERFORMANCE" name="PERFORMANCE">1.4 Performance</a></h1>
<p>
Performance Management provides functions to evaluate and report upon the behaviour of
telecommunication equipment and the effectiveness of the network or network element. Its role is to
gather and analyse statistical data for the purpose of monitoring and correcting the behaviour and
effectiveness of the network, network elements or other equipment and to aid in planning, provisioning,
maintenance and the measurement of quality.
</p>
<small>
Reference <a href="http://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-M.3400-200002-I!!PDF-E&type=items">TU-T M.3400 (02/2000)</a>
</small>

</div>


<!------------------ 1.5 Security ---------------------------------------->
<div class="SECT5">
<h1 class="SECT5"><a id="SECURITY" name="SECURITY">1.5 Security</a></h1>
<p>
Security Management provides for the management of security. Security of Management functionality includes Security services for communications and Security event detection and reporting:
<br><br>
Security services for communication provide the services for authentication, access control, data confidentiality, data integrity, and non-repudiation that may be exercised in the course of any communications between systems, between customers
and systems, and between internal users and systems. 
<br><br>
In addition, a set of pervasive security mechanisms are defined, so that they are applicable to any communication (such as event detection, security audit trail management and security recovery). 
<br><br>
Security event detection and reporting report to higher layers of security any activity that may be interpreted as a security violation (e.g. unauthorized user, physical tampering with equipment, etc.).
<br><br>
Security Management includes the following function set groups:
</p>

<ul>
	<li>
	<p>Prevention</p>
	</li>

	<li>
	<p>Detection</p>
	</li>

	<li>
	<p>Containment and recovery</p>
	</li>

	<li>
	<p>Security administration</p>
	</li>
</ul>
<small>
Reference <a href="http://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-M.3400-200002-I!!PDF-E&type=items">TU-T M.3400 (02/2000)</a>
</small>
</div>

</body>
</html>